prompt: record clipper-in-search-identifier as shipped (PyAutoFit#1493/#1494) - #249
Merged
Merged
Conversation
…3/#1494)
The identifier decision shipped in PyAutoFit on 2026-08-18 (f3767a7,
released 2026.8.20.1) while its prompt sat in draft/ — never issued, never
recorded. Option 2 was chosen: __identifier_fields__ = ("clipper",) on
AbstractMultiStartGradient and AbstractBFGS, re-keying existing multi-start
and (L)BFGS output directories, with the nested samplers, MCMC searches and
Drawer deliberately untouched and pinned byte-identical.
Writes the completion record with the decision and its reasoning (why not
options 1/3/4), the scoping constraint that keeps the nested-sampling
archive stable, and the residuals this does NOT claim done: the release
notes never state plainly that stored results re-key, the migration question
is unanswered, and option 4 (a loud .completed short-circuit) stays open.
Also refreshes five stale pointers that still described the question as an
open draft, including a SUPERSEDED banner over the phase-2 campaign
record's arm-collision trap — its three verified hashes were true on
2026-08-16 and false from 2026-08-18.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HhpuTLDVywbftqNbDopcBY
Jammy2211
pushed a commit
that referenced
this pull request
Aug 20, 2026
Jammy2211
pushed a commit
that referenced
this pull request
Aug 23, 2026
The merge commit regenerated dashboard.md/.html from a PyAutoBrain checkout that was 5 commits behind origin/main, three of which changed the dashboard generator (#249/#250/#251 — the Recent-feed work that PyAutoMind #270/#271/#272 landed). That reverted the paged Recent feed: dashboard.html lost 119 lines. PyAutoBrain updated to ad927eb and both files regenerated. The diff against main is now +24/-6 — the two new prompts entering the backlog, and nothing else. `intake dashboard --check` reports current. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015Mw2KC1M1HKrvTqe5zcEZn
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Retrospective lifecycle close-out. The decision this prompt asked for was made and shipped in PyAutoFit on 2026-08-18 (
f3767a7, PR #1494, closing issue #1493, released in 2026.8.20.1) — but the prompt never leftdraft/, so the Mind carried no record of it and four other records still pointed at it as an open question.The decision that shipped
Option 2:
__identifier_fields__ = ("clipper",)onAbstractMultiStartGradientandAbstractBFGS, unconditionally. Existing multi-start and (L)BFGS output directories re-key and stored results are orphaned — accepted deliberately as the cost of an identifier that tells the truth about what produced a result.Scoped to the searches that consume the clipper, not hoisted to
NonLinearSearch: nested samplers, MCMC andDrawerkeep byte-identical identifiers, pinned by regression tests plus a tripwire asserting the nested samplers never grow aclipperattribute.What this PR changes
complete/2026/08/clipper-in-search-identifier.md— the decision and its reasoning (including why options 1, 3 and 4 were not taken), the "a setting that cannot change the result must not re-key stored results" principle behind theDrawerexclusion, and the original prompt folded in under## Original prompt.draft/feature/autofit/clipper_in_search_identifier.md.complete/index.md,dashboard.md,dashboard.html.SUPERSEDEDbanner over the phase-2 campaign record's arm-collision trap, whose three verified identifier hashes were true on 2026-08-16 and false from 2026-08-18. The original measurement is left intact as the evidence that motivated the change.The record is explicit about what it does not claim is done: the release notes never state plainly that stored results re-key, the "is a migration wanted?" question is unanswered, and option 4 (refusing the
.completedshort-circuit when the search config differs) stays open.Validation
scripts/lifecycle.py check→ OK.scripts/lifecycle.py index --check→ OK. No registry entry to clear — the task never enteredactive.md,planned.md,parked.md,queue.mdorideas.md, which is exactly why the drift guard could not see it.🤖 Generated with Claude Code
https://claude.ai/code/session_01HhpuTLDVywbftqNbDopcBY
Generated by Claude Code